Planned Items - Defines the number of items(User story, Task, Bugs) committed by all folks during the sprint planning.
Ad Hoc Items - Defines the numbers of items (User story, Task, Bugs) added to the ongoing sprint on priority.
Completed Items - Defines the numbers of items (User story, Task, Bugs) completed in the sprint but the count does not include the Ad-hoc and unplanned Items
Unplanned Items - Defined the number of items (User story, Task, Bugs) added after the beginning of the sprint but not part of the original sprint plan.
DOD - Definition of Done , should be added to the ticket as comment or description on what the status of the ticket should be by the end of the sprint.
Shift Left testing approach . Finding Impact areas by QA in development phase(before testing) , helps the developer to covers missed areas in development phase.
Communication among the team .Sales 360 standup helps the team to conveys their daily status progress and blockers if they are facing . Resolving blockers within sales 360 standup helps the team to move fast forward.
Timeline for each tickets is clearly mentioned
Team taking ownership on assigned task, delivering them on committed timeline
Actual work is progressing
Sticking to the scope of the ticket -For feature Label renaming(Lead score to score and owner) we have adding the scope of the ticket while ticket is testing
Temp feature check should have been implemented in prior . Developer reworking on existing code they have committed to accommodated the changes (in both backend and frontend) . +2
Planning items in-prior to sprint planning not in the middle of the spint .
Ticket Updation - Adding work progress , updating acceptance criteria and stand/decision taken.
Sales 360 standup is high level status update . so we will continue to have daily squad standup to get updates.
Appreciations
Meenakshi +3 - Sharing impacted areas to developers before the ticket is Ready for QA .
Action Items:
→ Freshrelease ticket updation - For update in acceptance criteria and Decision/Stands taken .
→ Setup calendar-Informing planned leaves to the team
Communication among team for calling out and resolving issues +1
Act with urgency and commitments towards work on sales 360 items +1
Onboarding the new comers to the squad
QA involvement in finding impact areas and writing test cases before feature in Ready for QA
Time spent to work on Reducing automation pipeline
Complete integration setup in Docker Environment needs to be there as in staging to test everything before signing off in branch +1
Trinity docker is deleted and is not communicated to the team. we figured out while testing .
ETA timeline issues - unable to work on SLA Metrics(Adding Rspec/Ember/Automation test cases) for last name optional feature. since we have updated the ETA .
Freshchat integration is not be working in dockers and is not communicated to team.
Venkat NarayananNivedita Peddiraju +2 - Tremendous effort on Last name optional feature.Taking ownerships and communicating issues to PM .
Meenaloshani Murugan +1-Handling and tracking testing last name optional feature
Action Items:
->Integration setup in Docker Environment needs to be there as in staging to test everything before signing off in branch testing - Akshayvaliya Rakkanchath
Squad Rspec percentage got increased (85%) as we assigned Rspec ticket for Tamizhselvan R in this sprint and achieved 100% coverage on file crm_data_migration_util.rb
Abishek in speed mode helps the team to delivered tickets within in the sprint- FSALES-16567,18175,17497.Kudos to Abishek Kumar S
Getting import errors logs through mails.Helping team to resolve/getting insights on issues without depending on others .Thanks for the initiative Irfan Shaik.+1
Irfan and Nivedita is doing initial code review , before send to bhagi .
We picked up unplanned items (7) and delivered it in sprint.
sync between PM before handing over the requirement to Engineering team. i.e , Issue in adding Twitter in group mandatory fields as part of last name feature.+1
Past two sprint , we were not doing story grooming . Need to have tickets in hand before doing sprint planning.+1
Proper Estimation and Speed up the development and testing - Last name , Subscription type and status feature is spilled over from last 4 sprints.+1
Freshrelease ticket Updation on daily basis
Proactive communication on Blockers and Issues and owning the problems/issues.
Last name went to production without any issues. Extraordinary work on Last name optional feature as it has major impact in all over areas , we shipped it smoothly .
Working remotely (WFH) is working well
Sprint ceremonies are going regular
Work Progress happening
People are helping each other and responding on time
Lack of Backlog tickets and planned pipeline is missing . We should have tickets before sprint planning- +3
Full attendance in squad standup . As we are working remotely , we would like to connect with everyone in stand-up and sharing the things. +2
Need to improve the communication - As we are doing WFH, we should be proactive/over communicated when communicating the blockers,asking peers help.
Focusing on L2 tickets - As we are occupied with sales 360 items , we are missing SLA on some of L2 tickets.
Tracking the Import Failures/Errors logs in Production environment.We have found two major root causes for the failures and fixed one issue in this sprint.(For reference,FSALES-19895,19705).+3
Sprint Planning went well.We allocated two resources for resolving L2 issues . In sprint beginning days , we are having 8 overdue tickets . It helps us to resolve those tickets and maintaining SLAs.+3
Sprint ceremonies went well. Active Participations in daily standups .+2
Involving multiple Devs and QA into single Epic(for this sprint we are having Color changes) and shipping them out .That strategy is working out.
Color changes Feature:Communication and Collaboration between team(Designer,Devs,QAs) is going Good. Three squads are working on this item and Playing as a team and resolving the stuffs.+2
Subscription Status and Types :
Getting requirement changes in the middle of testing .Many breakages in the impact ares because of changing requirements .
QA and Impact areas review can also be checked with other squad QAs to avoid the bug leakages.
We were not picking any major item in this sprint apart from subscription types and status and color changes.
Ticket updation with the detailed description in Acceptance criteria and Record the conversation/tech discussion in tickets. It will helps the people to get the progress . +2
.
Appreciations
Abishek Kumar S -Proactively monitoring and resolving L2 tickets and tracking import errors - +4
Nivedita Peddiraju -For helping and mentoring tamizh .Resolving blockers in his path.And Resolving L2 tickets .+3
We have pulled in dev tasks than whole tickets for the tickets that Definition of Done is Dev completed
Improvement in L2 resolution
Sprint Planning went well -+2
Tickets were identified/shared before the ceremony
Tickets assigned to individuals
Sliced epics(timeline feeds, custom for sales 360 GA item) into smaller tickets i.e, Tech implementation, pre-requisite and completing them in this sprints. +2
Following up on last sprint action items - Test case reviews is done before actual testing
Surface issues in staging to stakeholders +1
Identify and test more impact areas
Adding existing cases during impact regression
L2 Resolution:
Update agent
Update the comments with the progress info
Find the temporary solution/hacks to cool down the customers if the permanent fix is hard and taking time.
Pick up tickets on priority
Tickets in review state for long time . Individual assignee bring this in standup incase any showstoppers
.
Appreciations
Tamizhselvan R Contribution in Rspec test cases when he is done with his assigned task
Discussing feature blockers/L2 tickets after standup +2
L2 addressed on time and no SLA breached ticket in this sprint +2
Dev fixing the bugs proactively that helps QA proceed the testing without blockers
Bundle signup helps the team to perform integration testing in docker
Good work in Timeline feeds ,Custom Roles tickets . Tickets are on track . + 3
Collaboration between cross team(FM ,Fchat ,FCaller,MCR) in Integration testing went well +1
Dev/QA owner of the ticket is not notified when there is mock change +3
Requirement came in at the end of development . Because of this , we are not able to meet the Definition Of Done(Dev complete) of lead management ticket .
Bundle signup , Docker setup for integration testing-Taking time
Documenting the docker set up issues with FAQs will helps others to resolve the issues quickly
Kishore Shanmugam - Lead Management - Good quality of code in lead management . Spending time on weekends to fixing the bugs . Calling out blockers to stakeholders and ticket updation .+ 2
Migration tickets needs to be completed within estimated time(Both testing and dev) + 2
If the person is done with the assigned tickets in the sprint, he/she might pick up the ticket that could be a spillover from another person's(in ready for dev status)
-BE dependent on Rakesh squad due to onboarding items .Get ETA for ETA
BE testing in progress.. (dev testing)Mobile testing started from
As discussed on 29 Sep Mobile will go live by (date to be finalised after 3rd oct ) post which matrix team will turn on the flag and fix other fileds to support 16 digits (ETA not confirmed)
Delayed docker received by Matrix squad received on 13 Oct from 03 Oct
-
Android
S
Dev Testing -
16 Aug 2023 18 Oct 2023 31 Oct 2023
DONE
Dev ETA - Aug 9
(Dev testing)QA ETA - 25 Sep
Store upload date- 6 Nov
-BE dependent on Rakesh squad due to onboarding items
BE testing inPorgress.. Mobile testing stared from
- As discussed on 29 Sep Mobile will go live by (date to be finalised after 3rd oct ) post which matrix team will turn on the flag and fix other fileds to support 16 digits (ETA not confirmed).
Delayed docker received by Matrix squad received on 13 Oct (03 Oct)
- ETA moved from 31 Oct to 3 Nov as we have planned to club with custom module release. Also build delivery was delayed by 2 days( Oct 25 to Oct 27)
Spike to be picked from 12th, provided docker is available from 9th.
Docker will be shared by 7th July
Dev to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.
ETA for ETA-
gone live by Sep 1
Android
S
27 Sep 2023
6 Oct 2023
DONE
Dev ETA - 20 Sep
QA start date : 20 Sep
QA ETA - 21 Sep
Store upload date - 6 Oct
Spike to be picked from 12th, provided docker is available from 9th.
Docker will be shared by 7th July
Dev to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.
ETA for ETA-
ETA- Sep 20 ETA- SEP 27 (merged to staging)
Store upload extended to Oct 5 for L4 completion
Quick Wins
Mobile : Dowloading/ Saving CPQ Documents as PDF FSALES-85612
iOS
XS
Aug 20
Sep 27
No QA testing - dev testing
no QA testing - dev testing
Oct 6
DONE
aug 17 - aug 30 sprint ---- Dev was completed and release was blocked due to API dependency Aug 31 - Sep 13 — was on hold Sep 14- Sep 27 - merged to staging Oct 6 - Uploaded to store
Changes/modifications agreed halfway during execution has to be incorporated in mocks then and there itself. Design team has to Own this update. TPM to set the expectations with Design.
